Dynamic numerology based on services

ABSTRACT

A base station can select orthogonal frequency-division multiplexing (OFDM) numerologies that define subcarrier spacing values based on attributes associated with one or more services that a user equipment (UE) is using. The base station can use the selected OFDM numerologies for transmission associated with the services. When the UE is using multiple services simultaneously, the base station can select the same or different OFDM numerologies for the multiple services.

RELATED APPLICATIONS

This U.S. patent application is a continuation of, and claims priorityto, U.S. patent application Ser. No. 16/004,240, filed on Jun. 8, 2018,which claims priority to provisional U.S. Patent Application No.62/625,164, entitled “Dynamic Numerology with Services in Wireless,”filed on Feb. 1, 2018, and provisional U.S. Patent Application No.62/646,281, entitled “Dynamic Numerology with Services in Wireless,”filed on Mar. 21, 2018, the entirety of which are incorporated herein byreference.

BACKGROUND

Multiplexing can be used to combine and transport multiple signals overa channel bandwidth. One type of multiplexing often used in wirelessaccess technologies is orthogonal frequency-division multiplexing(OFDM). OFDM transmits data in multiple subcarriers within a largerchannel bandwidth. To mitigate interference between the subcarriers, thesubcarriers can be spaced apart according to a subcarrier spacing.

Some wireless access technologies, such as Long Term Evolution (LTE),use an OFDM numerology with a fixed subcarrier spacing. However, otherwireless access technologies, such as fifth generation (5G) New Radio(NR), use flexible OFDM numerologies that allow scalable subcarrierspacing. Different subcarrier spacing values in these flexible OFDMnumerologies can have different benefits in different situations.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items or features.

FIG. 1 depicts an exemplary environment in which user equipment (UE) canaccess services through a telecommunication network.

FIG. 2 depicts an example in which a base station supports transmissionsin frequencies corresponding to multiple bands.

FIG. 3 depicts a protocol stack that can be used by UEs and basestations in 5G New Radio (NR) communications.

FIG. 4 depicts an example OFDM waveform, in which data can betransmitted in subcarriers spaced apart by a subcarrier spacing.

FIG. 5 depicts an example of an OFDM waveform in which subcarrierspacing can vary between different subcarriers.

FIG. 6 depicts an example system architecture for a base station.

FIG. 7 depicts a flow chart of an exemplary process for selecting anOFDM numerology for data of a service when a handover operation isperformed.

FIG. 8 depicts a flow chart of an exemplary process for assigning OFDMnumerologies for multiple services being used by a single UE.

DETAILED DESCRIPTION Introduction

Wireless access technologies can use multiplexing, such as orthogonalfrequency-division multiplexing (OFDM), to combine and transportmultiple signals over a channel bandwidth. OFDM transmits data encodedinto OFDM symbols in parallel using multiple subcarriers that are spreadout over a larger carrier's channel bandwidth based on subcarrierspacing values. Subcarrier spacing can cause the subcarriers to beorthogonal in the frequency domain, thereby mitigating interferencebetween the subcarriers.

Some wireless access technologies, such as Long Term Evolution (LTE),use an OFDM numerology in which the subcarrier spacing is fixed at 15kHz. However, other wireless access technologies allow other OFDMnumerologies that can vary the subcarrier spacing and/or other OFDMparameters. For example, 5G New Radio (NR) is being developed to allowscalable subcarrier spacing in which the subcarrier spacing can be setat different values including 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240kHz.

Different OFDM numerologies that use different subcarrier spacing valuescan provide different benefits. For example, smaller subcarrier spacingvalues can lead to larger OFDM symbol durations, which can maketransmissions more resilient to multi-path delay spread. As anotherexample, larger subcarrier spacing values can lead to smaller OFDMsymbol durations, which can make transmissions less sensitive to phasenoise and/or increase how frequently data can be transmitted.

Accordingly, a telecommunication network may want to use different OFDMnumerologies for the same user equipment (UE) in different situations.One proposed solution associates different OFDM numerologies withdifferent bandwidth parts. In this solution, the frequencies of acarrier's channel bandwidth can be divided into multiple bandwidthparts. Individual bandwidth parts can be designated as active for UEs,such that UEs can save power by only scanning frequencies within theactive bandwidth parts instead of the carrier's full channel bandwidth.Communications between a UE and a base station can use different OFDMnumerologies that are associated with different bandwidth parts,depending on which bandwidth part is currently designated as active. Thetelecommunication network can accordingly indirectly change which OFDMnumerology is used for a particular UE by sending downlink controlinformation (DCI) to the UE that changes the active bandwidth part toanother bandwidth part that is associated with a different OFDMnumerology.

However, solutions that indirectly change OFDM numerologies based onactive bandwidth parts only allow one OFDM numerology to be used for aUE at a time, depending on which bandwidth part is currently active. Assuch, even if different OFDM numerologies would be suitable for multipledifferent services that a single UE is using simultaneously, data forthe multiple services could only be transmitted using the one OFDMnumerology tied to the active bandwidth part. Moreover, instructing a UEto change the active bandwidth part in order to indirectly change theOFDM numerology can cause delays. For example, in some cases a UE'sradio may take 50 us to 900 us to tune to a different bandwidth part,which may be too long for low-latency services.

Additionally, when different OFDM numerologies are tied to differentbandwidth parts in different frequency bands and a UE moves to a newlocation that is better served by a different frequency band, anindirect OFDM numerology change may occur if a handover operationchanges communications with a UE from an active bandwidth part in onefrequency range to a new active bandwidth part in another frequencyrange that is better suited for the UE's new location. However, suchhandover operations are generally performed based on signal qualitymeasurements reported by the UE to the telecommunication network, notbecause the telecommunication network intended to change the OFDMnumerology for the UE to a different OFDM numerology better suited to aparticular service that the UE is using. Accordingly, even after amobility handover operation, the new OFDM numerology would be one linkedwith the new active bandwidth part, not an OFDM numerology selectedbecause it is best suited for services that the UE is using.

This disclosure describes systems and processes through which a basestation of a telecommunication network can dynamically assign one ormore OFDM numerologies to a single UE, based on one or more servicesthat a UE is using. Unlike solutions that indirectly assign OFDMnumerologies solely on physical layer considerations such as an activebandwidth part, changing OFDM numerologies based on services can be anend-to-end solution that also involves a service layer, a media accesscontrol (MAC) layer, and/or other higher protocol layers at a basestation.

Example Environment

FIG. 1 depicts an exemplary environment in which user equipment (UE) 102can access services through a telecommunication network by connecting toone or more base stations 104 linked to a core network 106. The UE 102,base stations 104, and/or core network 106 can be compatible with one ormore wireless access technologies, such as fifth generation (5G)technologies, Long Term Evolution (LTE)/LTE Advanced technology,Licensed Assisted Access (LAA), High-Speed Data Packet Access(HSDPA)/Evolved High-Speed Packet Access (HSPA+) technology, UniversalMobile Telecommunications System (UMTS) technology, Code DivisionMultiple Access (CDMA) technology, Global System for MobileCommunications (GSM) technology, and/or any other previous or futuregeneration or type of wireless access technology.

A UE 102 can be any device that can wirelessly connect to thetelecommunication network via one or more base stations 104. Forexample, a UE 102 can be a smart phone, a cellular phone, a personaldigital assistant (PDA), a personal computer (PC), a laptop, a desktop,a workstation, a media player, a tablet, a gaming device, a smart watch,an Internet of Things (IoT) sensor or device, a controller for anautonomous car, or any other type of computing or communication device.

Base stations 104 can be part of an access network that links connectedUEs 102 to the core network 106. Some base stations 104 can include agNode B (gNB) that uses 5G New Radio (NR) wireless access technology toconnect to UEs 102. In some examples, a base station 104 can also, oralternately, include an eNode B (eNB) that uses LTE wireless accesstechnology to connect to UEs 102, and/or elements compatible with anyother wireless access technology. Example architecture for base station104 is illustrated in greater detail in FIG. 6, and is described indetail below with reference to that figure.

A core network 106 can include control nodes that can manage networkresources for connections with particular UEs 102. The core network 106can also include gateways that link the core network 106 to basestations 104 and/or to packet data networks (PDNs) 108, such as an IPMultimedia Subsystem (IMS), the Internet, and/or other networks outsidethe core network 106. For simplicity, elements of the core network 106are not illustrated.

A UE 102 can engage in various services through a connection to the corenetwork 106 via one or more base stations 104. For example, a UE 102 canengage in a voice call in part by sending a request through the corenetwork 106 to an IMS that sets up and manages voice calls. As anotherexample, a UE 102 can engage in web browsing, data downloads, mediastreaming, and many other services through a connection to the Internetthat passes through the core network 106. Individual services may havevarious performance goals or requirements related to factors includinglatency, reliability, throughput, positioning, and availability.

Services that a UE 102 can engage in can be broadly grouped intocategories, including, but not limited to, enhanced mobile broadband(eMBB), ultra-reliable low latency communications (URLLC), massivemachine type communications (mMTC), and mobile Internet of Things(M-IoT). eMBB services can be services for which a high throughput isdesired, such as high definition video streaming and high-speed filetransfers. URLLC services can be services for which a high reliabilityand/or low latency is desired, such as data transfers for remote surgeryor control of flying drones or self-driving cars. mMTC and/or M-IoTservices can be services for devices that may be densely populated, suchas services for IoT devices and sensors. 5G NR is being developed tosupport eMBB, URLLC, and mMTC use cases.

A telecommunication network and individual UEs 102 can support multiplenetwork layers based on different wireless access technologies and/ordifferent frequency bands. As discussed above, a telecommunicationnetwork and UEs 102 can support multiple wireless access technologies,including 5G NR and LTE, and those wireless access technologies may usedifferent frequency bands. For example, 5G NR can operate with differentdeployments in a wide range of frequencies extending from below 1 GHz to100 GHz or beyond. In some examples, frequencies from 600 MHz to 1 GHzcan be considered low bands for 5G NR, frequencies from 1 GHz to 6 GHzcan be considered middle bands for 5G NR, and frequencies from 6 GHz to100 GHz can be considered high bands for 5G NR, with bands above 24 GHzbeing referred to as millimeter wave (mmWave) bands. However, thesespecific frequency ranges are only examples, and in other casesdifferent frequency ranges can be considered low, middle, and high bandsfor 5G NR.

Within supported frequency bands, actual transmissions can occur withinindividual carriers that have smaller channel bandwidths. For example, a5G NR base station 104 can be configured to use a 600 MHz band known asn71 in 3GPP standards, but send data within carriers that have channelbandwidths of 5 MHz, 10 MHz, 15 MHz, or 20 MHz in that 600 MHz band. Inthis example, if a carrier with a channel bandwidth of 5 MHz is used inthe 600 MHz band, a 5G NR base station 104 can be configured to use anyunlimited and/or cleared Resource Block within the carrier, in somecases via bandwidth parts selected from the larger carrier.

FIG. 2 depicts an example in which a base station 104 supportstransmissions in frequencies corresponding to a 5G high band,frequencies corresponding to a 5G middle band, and frequenciescorresponding to a 5G low band and/or an LTE band. As shown in FIG. 2,in some examples the frequencies of the 5G high band can cover a cellwith a smaller geographical area than a cell covered by the frequenciesof the 5G middle band, while the frequencies of the 5G low band and/orLTE band can cover a cell with a larger geographical area than the cellcovered by the frequencies of the 5G middle band.

A UE 102 can have one or more antennas that cause it to be compatiblewith multiple wireless access technologies and/or frequency bands. Insome cases, this compatibility can allow a UE 102 to connect to atelecommunication network using multiple wireless access technologiesand/or frequency bands simultaneously. In other cases, thiscompatibility can allow a UE 102 to transition between using differentwireless access technologies and/or frequency bands at different times,such as moving from an overlay 5G network to an LTE network. As anexample, when a UE 102 physically moves from a location covered by a 5Ghigh band into a location covered by a 5G middle band as shown in FIG.2, a handover operation can be performed so that the communicationsbetween the base station 104 and the UE 102 use frequencies in the 5Gmiddle band instead of frequencies in the 5G high band.

In some cases, base stations 104 can assign UEs 102 to particularnetwork layers based on admission control and/or load control policies.For example, when a UE 102 is first turned on and connects to a basestation 104, admission control and/or load control policies can be usedto instruct that UE 102 to connect to a particular base station 104 viaa particular wireless access technology and/or frequency band, such asassigning a UE 102 to connect to a base station 104 via LTE if 5G NRresources are not currently available. After this initial connection,load control policies can be used to handover a UE 102 between basestations 104 and/or network layers. For example, if a UE 102 wasinitially assigned to an LTE network layer, but 5G NR resources laterbecome available, communications for the UE 102 can be switched to a 5Gnetwork layer.

FIG. 3 depicts a protocol stack that can be used by UEs 102 and basestations 104 in 5G NR communications. The 5G NR protocol stack includesprotocol layers involved in a user plane, including a Service DataAdaptation Protocol (SDAP) layer 302, Packet Data Convergence Protocol(PDCP) layer 304, a Radio Link Control (RLC) layer 306, a Media AccessControl (MAC) layer 308, and a physical (PHY) layer 310. In the controlplane, the 5G NR protocol stack can include a Radio Resource Control(RRC) layer 312, the PDPC layer 304, the RLC layer 306, the MAC layer308, and the physical layer 310. In some cases, the RRC layer 312 can belinked directly to the physical layer 310, as well as to the PDPC layer304. Communications using other wireless access technologies can involvesimilar protocol stacks, although some, including the LTE protocolstack, may lack an upper SDAP layer 302 in the user plane.

At the SDAP layer 302, a Quality of Service (QoS) flow can be mapped toa particular data radio bearer between a UE 102 and a base station 104,and a corresponding QoS flow ID can also be marked in data packets ofthe QoS flow. Accordingly, a base station 104 can identify trafficassociated with particular services or service categories, and/ordesired performance attributes for those services or service categories,at the SDAP layer 302 based on parameters such as a QoS flow ID and/oran associated QoS Class Identifier (QCI).

PDCP layer 304 functions can include header compression, ciphering, andintegrity protection. RLC layer 306 functions can include errordetection, segmentation, and resegmentation. MAC layer 308 functions caninclude error correction, scheduling, and prioritization, as well asother functions described below.

At the physical layer 310, data can be sent or received using an airinterface associated with a wireless access technology. When a basestation 104 sends data, the base station's physical layer 310 canreceive data from the MAC layer 308 and wirelessly transport that dataover the air in a waveform. A multiplexing scheme, such as orthogonalfrequency-division multiplexing (OFDM), can be used at the physicallayer 310 to transmit multiple data streams simultaneously. For example,a base station 104 can use OFDM to transmit different data streams toone or more UEs 102.

As will be described in more detail below, an OFDM numerology forcommunications with a UE 102 can be selected at a base station's MAClayer 308 and be implemented at the physical layer 310. Additionally, anassignment of the selected OFDM numerology can be sent from the basestation's RRC layer 312 to the UE 102 via the physical layer 310, toinform the UE 102 which OFDM numerology will used.

FIG. 4 depicts an example OFDM waveform, which can be used to combineand transport multiple signals over a carrier's channel bandwidth. InOFDM, data streams can be encoded into OFDM symbols in part based onoperations such as an inverse Fourier Transform. A receiver can performan operation, such as a Fourier Transform, on received OFDM symbols torecover an original data stream.

OFDM symbols for different data streams can be transmitted in parallelusing different subcarriers 402, which can lead to a high spectralefficiency relative to many other modulation schemes. The subcarriers402 of an OFDM waveform can be spread out over a larger carrier'schannel bandwidth based on subcarrier spacing 404 that causes individualsubcarriers 402 to be orthogonal in the frequency domain. For example,as shown in FIG. 4, subcarrier spacing 404 can be chosen such that peaksof individual subcarriers 402 are positioned at frequencies where othersubcarriers 402 have nulls. This orthogonality can mitigate interferencebetween the subcarriers 402.

In some cases, because multipath propagation can cause a loss oforthogonality between subcarriers 402, portions of the ends of the OFDMsymbols can be added to the beginning of the OFDM symbols as cyclicprefixes (CPs). The CPs can serve as guard intervals that space out theOFDM symbols, and/or can help a receiver distinguish between the OFDMsymbols. In some examples, normal or extended CP types can be used indifferent situations or with certain subcarrier spacing 404 values, aswill be discussed further below.

The subcarrier spacing 404 can be inversely proportional to the lengthof the OFDM symbols, such that larger subcarrier spacing 404 values canbe associated with shorter OFDM symbols, while shorter subcarrierspacing 404 values can be associated with longer OFDM symbols. In somecases, the length of CPs can similarly scale depending on the subcarrierspacing 304 in order to maintain a ratio of the length of the CPs to theoverall length of the OFDM symbols.

An OFDM numerology can refer to a subcarrier spacing 404 value, a CPtype, and/or any other attribute that describes an OFDM waveform.Accordingly, in some examples one or more OFDM numerologies can be usedfor communications with a UE 102 depending on selected subcarrierspacing 404 values, selected CP types, and/or other factors.

In some wireless access technologies, the subcarrier spacing 404 can befixed at a specific value. For instance, in LTE the subcarrier spacing404 is generally fixed at 15 kHz. However, in 5G NR and some otherwireless access technologies, the subcarrier spacing 404 can be scalableto different values. This can allow the subcarrier spacing 404 to varybetween different subcarriers 402 in 5G NR transmissions, as shown inthe example of FIG. 5. In particular, the scalable subcarrier spacing404 in 5G NR can be set at values determined by the equation 2^(μ)·15kHz, where μ is a non-negative integer. Subcarrier spacing 404 in 5G NRcan accordingly be set at values including 15 kHz, 30 kHz, 60 kHz, 120kHz, and 240 kHz. In some examples, different OFDM numerologies can bereferred to using different values for μ, as different values for μ candefine different subcarrier spacing 404 values.

Because different subcarrier spacing 404 values can be associated withOFDM symbols of different lengths, different numbers of OFDM symbols canbe sent during the same period of time when different OFDM numerologiesare used. For example, data can be scheduled to be sent within subframesof 1 ms each, with ten subframes fitting into a 10 ms radio frame.Depending on the subcarrier spacing 404, such subframe can have adifferent number of slots for OFDM symbols. When different OFDMnumerologies are used, the different OFDM numerologies can align on OFDMsymbol boundaries in the time domain, such as every 1 ms betweensubframes.

The number of OFDM symbols that can fit into each slot can varyaccording to a CP type. In some examples, a normal CP type can allow 14OFDM symbols to fit into each slot, while an extended CP type can allow12 OFDM symbols to fit into each slot. In some examples, a normal CP canbe used with subcarrier spacing 404 values of 5 kHz, 30 kHz, 60 kHz, 120kHz, and 240 kHz, while an extended CP can also be used with a 60 kHzsubcarrier spacing 404. The table below shows a non-limiting example ofdifferent OFDM numerologies associated with different subcarrier spacing404 values and CP types, which can vary the number of slots per subframeand thus the total number of OFDM symbols that can be sent per subframe.

Number of Number of Subcarrier Number of Slots OFDM Symbols Spacing OFDMSymbols per 1 ms per 1 ms μ and CP Type per Slot Subframe Subframe 0 15kHz 14 1 14 (Normal CP) 1 30 kHz 14 2 28 (Normal CP) 2 60 kHz 14 4 56(Normal CP) 2 60 kHz 12 4 48 (Extended CP) 3 120 kHz  14 8 112 (NormalCP) 4 240 kHz  14 16 224 (Normal CP)

In some cases, a smaller subcarrier spacing 404 value can be desiredbecause the associated OFDM symbols are larger, even though fewer can betransmitted during a given period of time. For example, because largerOFDM symbols include larger CPs copied from the ends of OFDM symbols, asmaller subcarrier spacing 404 value might be used when copies of thedata at the ends of OFDM symbols may be needed to reliably decode theOFDM symbols. On the other hand, in some cases a larger subcarrierspacing 404 value can be desired because the associated OFDM symbols aresmaller and can be transmitted more frequently.

Although multiple OFDM numerologies may be possible, a base station 104can assign one or more OFDM numerologies for communications with a UE102 based on parameters of one or more services being used by that UE102. In some cases, in addition to parameters of services being used bythe UE 102, the base station 104 can also select one or more of theallowable ODFM numerologies for communications with the UE 102 based onnetwork attributes, operator policies, and/or other factors.

When a UE 102 is initially turned on or moves into a cell, it can attachto a base station 104 and be synchronized to the telecommunicationnetwork in the control plane. The base station 104 can broadcast systeminformation from the RRC layer 312, such as in System Information Blocksor Synchronization Signal Blocks. This system information can include adefault ODFM numerology used by the base station 104, such that the UE102 can use that default ODFM numerology to communicate with the basestation 104. After a UE 102 has attached to a base station 104 using adefault ODFM numerology, the UE 102 can request initiation of one ormore services through its connection to the core network 106 via thebase station 104.

When a UE 102 engages in a service, data packets associated with theservice can pass through a base station 104. As described above, datafor the service can be encoded and transmitted between the UE 102 andthe base station 104 in one or more subcarriers 402 of an OFDM waveformat the physical layer 310. However, the base station 104 can analyzedata packets at one or more protocol layers above the physical layer 310to identify service attributes, determine service parameters associatedwith the service attributes, and use the service parameters to select anassociated OFDM numerology to use for transmissions associated with theservice. For example, the base station 104 can review data packets of arequest for a new service, determine an OFDM numerology to use for thatservice, and then use that OFDM numerology for subsequent transmissionsassociated with the service. The base station 104 can also inform the UE102 of the selected OFDM numerology via an RRC reconfiguration message,via downlink control information (DCI) in a Physical Downlink ControlChannel (PDCCH), or via any other type of message.

In some examples, data packets for a particular service can betransmitted as part of a flow associated with a QoS Flow ID, which in 5GNR can be analyzed at a base station's SDAP layer 302. The base station104 can accordingly use a QoS flow ID associated with data packets of aservice to determine a QCI and/or one or more QoS parameters associatedwith the service. In other examples, a base station 104 can also, oralternately, evaluate IP addresses or other information in headers ofdata packets at one or more protocol layers above the physical layer310. Such header information can be used to identify a server that issending or receiving the data packets, and accordingly to identify aservice known to be associated with that server.

In still other examples, the core network 106 can review traffic fordifferent services from one or more UEs 102 connected to one or morebase stations 104, and categorize or identify services for the basestations 104. For example, a core network 106 can group service intoservice instances for smartphones, autonomous cars, virtual reality,video and sports, IoT remote sensors and meters, and other applications.The core network 106 can map services instances into different networkslices and inform base stations 104 which network slices and associatedservice instances or types of services they are to handle.

The base station 104 can use the identity of a service and/or one ormore other attributes associated with the service to determine desiredperformance goals or requirements. For example, one or more serviceattributes can reflect performance requirements or goals related tofactors such as latency, reliability, availability, data rate, or packetloss. Other service attributes can be associated with a QCI, QoSparameters, Quality of Experience (QoE) parameters, a priority level, apackage length, a Service Profile Identifier (SPID), an Allocation andRetention Policy (ARP) that indicates a priority level for theallocation and retention of bearers and can be used to decide whether toaccept a request to establish a bearer or reject the request if networkresources are limited, and/or any other parameter than can indicate aservice attribute. The base station 104 can use the service attributesto select a OFDM numerology that provides benefits corresponding to theservice parameters.

In some cases, the base station 104 or the core network 106 cancategorize a service, based on its service attributes, as being an eMBBservice, a URLLC service, or an mMTC service. For example, a serviceassociated with a QoS Flow ID that corresponds to QoS parametersindicating that data for the service should be delivered at a highpriority and at a low latency may be considered a URLLC service. Asanother example, a service associated with QoS parameters indicatingthat data for the service is to be delivered at a high guaranteedbitrate may be considered an eMBB service. In some cases, the basestation 104 can be preconfigured with specific OFDM numerologiesassociated with an eMBB service category, an URLLC service category, andan mMTC service category. Accordingly, the base station 104 can assignan OFDM numerology to traffic of a service based on the service'sclassification as an eMBB service, URLLC service, or mMTC service.

In some cases, a base station 104 can alternately, or additionally,review individual service attributes to determine an OFDM numerology fora service. For instance, when a service attribute indicates that lowlatency is desired for the service, the base station may select an OFDMnumerology with a relatively large subcarrier spacing 404 associatedwith relatively small OFDM symbols, because smaller OFDM symbols can betransmitted more frequently than larger OFDM symbols and thereby assistwith lowering latency.

In some examples, a base station 104 can determine a subset of allowableOFDM numerologies based on an initial categorization of a service as aneMBB service, URLLC service, or mMTC service, and then choose aparticular OFDM numerology from that subset based on the service'sspecific attributes. For instance, a base station 104 or core network106 may initially categorize a service as an eMBB service, such that thebase station 104 can determine that a preconfigured subset of OFDMnumerologies for eMBB services includes 30 kHz and 60 kHz subcarrierspacing 404. Out of that subset, the base station 104 can then choose 60kHz subcarrier spacing 404 because the service's specific latency goalsare better served by longer OFDM symbols.

In some examples, a base station 104 can be configured a database thatassociates known services with specific OFDM numerologies, or subsets ofallowable OFDM numerologies. Accordingly, if a base station 104 or corenetwork 106 is able to identify a particular service from an IP headeror other information in these examples, the base station 104 can assignan OFDM numerology associated with that service in the list or database.

In addition to service attributes, in some examples a base station 104can also take into account network attributes and/or operator policieswhen dynamically assigning one or more OFDM numerologies to a UE 102.For example, a base station 104 may select an OFDM numerology forcommunications associated with a particular service based both onattributes of the service as well as on network attributes and/oroperator policies.

In some examples, network attributes can define specific frequency bandssupported by base stations 104 in licensed and/or unlicensed spectrum.For example, 5G NR base stations 104 can be set to use a 600 MHz bandknown as n71 in 3GPP standards, a 28 GHz band known as n257 in 3GPPstandards, and/or a 39 GHz band known as n260 in 3GPP standards. Networkconditions can also include radio frequency link conditions, keyperformance indicators, current loads on a base station 104 and/or otherbase stations 104, interference levels, mobility capabilities of UEs102, movement speeds of UEs 102, and/or other network conditions.

In some examples, operator policies can identify one or more allowableOFDM numerologies that are associated with frequency bands supported bythe base stations 104. For example, when 5G NR base stations supportn71, n257, and n260 bands as discussed above, an exemplary operatorpolicy can indicate that 15 kHz and 30 kHz subcarrier spacing 404 valuescan be used for data channels in the n71 band, while 60 kHz, 120 kHz,and 240 kHz subcarrier spacing 404 values can be for data channels inthe n257 and n260 bands. In this example, an operator policy canadditionally indicate that subcarrier spacing 404 of 15 kHz can be usedfor synchronization in the n71 band, subcarrier spacing 404 of 120 kHzcan be used for synchronization in the n257 band, and subcarrier spacing404 of 120 kHz or 240 kHz subcarrier spacing 404 can be used forsynchronization in the n260 band.

Additionally, in some examples operator policies can instruct a basestation 104 to select between specific OFDM numerologies based in parton particular channel bandwidths being used for a carrier. For example,an operator policy can indicate that a 5G NR base station 104 can use 15kHz subcarrier spacing 404 when a carrier in the n71 band has a 5 MHzchannel bandwidth, but can select between 15 kHz subcarrier spacing 404and 30 kHz subcarrier spacing 404 when a carrier in the n71 band has alarger channel bandwidth such as 10 MHz, 15 MHz, or 20 MHz.

Operator policies can also include other types of policies, such as flowcontrol policies, traffic splitting policies, policies related to celltypes and/or wireless access technologies, caching control policies,mobile management policies, service continuity policies, satelliteaccess policies, and fixed broadband access policies.

Flow control policies can, at a base station's PDCP layer 304, indicatehow traffic of flows for certain services or certain types of servicesshould be treated. A base station 104 can accordingly select an OFDMnumerology for traffic of a service that provides benefits thatcorresponds with goals in an associated flow control policy.

A traffic splitting policy can be used in radio resource management atbase stations 104 to split traffic among network layers or base stations104 based on service types. For example, a traffic splitting policy canindicate that data for voice calls should be delivered via LTE, whiledata for media streaming should be delivered via 5G NR. Accordingly, atraffic splitting policy can be used to determine which network layerscertain services should be delivered on, and accordingly which OFDMnumerologies are allowed for those network layers.

A cell type policy can indicate allowable OFDM numerologies based onwhether a cell is a macro cell, a small or micro cell, a femtocell, apicocell, or any other type of cell. A wireless access technology policycan indicate allowable OFDM numerologies based on whether a base stationuses LTE, 5G, or other wireless access technologies. A service policycan be related to the service attributes discussed above, and indicateallowable OFDM numerologies for specific types of services, such dataservices, voice services, services for IoT devices, video-based servicessuch as live streaming or virtual reality, vehicle-to-vehicle services,or any other kind of service. A caching control policy can indicateallowable OFDM numerologies based on delivery of content from a contentcaching application. A mobile management policy can indicate allowableOFDM numerologies for a UE 102 or a group of UEs 102 that use certainaccess technology changes for some or all connections. A servicecontinuity policy can indicate allowable OFDM numerologies that canprioritize minimal packet loss during inter and intra wireless accesstechnology changes for a UE 102. Satellite access and fixed broadbandaccess policies can indicate allowable OFDM numerologies for servicesprovided in part over satellite access or fixed broadband access.

As described above, after a UE 102 attaches to a base station 104 andcommunications have been established using a default OFDM numerologyidentified by the base station in system information broadcasts, the UE102 can begin engaging in one or more individual services. When the UE102 sends a request to initiate such a service, the base station 104 canuse service attributes, network attributes, and/or operator policies toselect a specific OFDM numerology to use for communications with the UE102 for that service. The base station 104 can also inform the UE 102 ofthe selected OFDM numerology for that service in an RRC reconfigurationmessage, in DCI in PDCCH, or via any other type of message. Accordingly,the selected OFDM numerology can be used to carry data in subsequenttransmissions associated with the service.

In some cases, the base station 104 can also determine and assign aparticular frequency band and/or carrier for transmissions associatedwith a specific service using a selected OFDM numerology. For example,the base station 104 may be configured to select between a high mmWavefrequency band along with an OFDM numerology with large subcarrierspacing 404 for URLLC services, a middle frequency band with an OFDMnumerology with medium subcarrier spacing 404 for URLLC services, eMBBservice, mMTC service, or M-IoT services, or a low frequency band withsmall subcarrier spacing 404 for eMBB services and other low latencyservices.

If a handover operation moves a UE 102 to a different network layer thatuses a different frequency band and/or wireless access technology, abase station 104 can accordingly review the service attributes, networkattributes, and/or operator policies to determine if an OFDM numerologyshould be changed. For example, a UE 102 may move from a location servedby a first 5G NR band that allows subcarrier spacing 404 values of 60kHz and 120 kHz to a new location served by a second 5G NR band thatallows subcarrier spacing 404 values of 15 kHz and 30 kHz. Iftransmissions for a particular service had been transmitted to the UE102 at a 60 kHz in the first 5G NR band, a base station 104 may changethe OFDM numerology to 30 kHz when the UE 102 moves to the second 5G NRband. However, if the second 5G NR band also allowed 60 kHz subcarrierspacing 404, the base station 104 may keep the OFDM numerology at 60 kHzfor transmissions associated with the service if allowed by othernetwork attributes and/or operator policies. As another example, if a UE102 moves from a 5G band to an LTE band and the subcarrier spacing 404for transmissions associated with a service had been set at a subcarrierspacing 404 above 15 kHz, the subcarrier spacing 404 can be changed to15 kHz because subcarrier spacing 404 is fixed at 15 kHz for LTE.

When the UE 102 is engaged in multiple services at the same time, thesame or different OFDM numerologies can be used for differentsubcarriers 402 used to transmit data for the different services. Forexample, when a UE 102 is engaged in different services that haveattributes that are best served by different OFDM numerologies, thosedifferent OFDM numerologies can be used for different subcarriers 402that transmit data of the different services for the same UE 102. Insome cases, different frequency bands can be used to transmit data fordifferent services for the UE based on different OFDM numerologies. Inother cases, different OFDM numerologies can be used to transmit datafor different services in the same frequency band, such as forsubcarriers 402 in different carriers within the same larger frequencyband.

In some example, when a base station 104 determines that a single UE 102is engaged in multiple services and some of the services share acategory, latency requirement, or other parameter, the base station 104can select a frequency band, carrier, and/or OFDM numerology for eachgroup of services with shared parameters. For instance, if a UE 102 isengaged in a first service and a second service that have similarparameters, as well as a third service that has different parameters,the base station 104 can assign a first OFDM numerology for the firstand second services, and a second OFDM numerology for the third service.

Example Architecture

FIG. 6 depicts an example system architecture for a base station 104, inaccordance with various examples. As shown, a base station 104 caninclude processor(s) 602, memory 604, and transmission hardware 606. Thememory 604 can store service attributes 608, network attributes 610,operator policies 612, and/or an OFDM numerology selector 614.

In various examples, the processor(s) 602 can be a central processingunit (CPU), a graphics processing unit (GPU), both CPU and GPU, or anyother type of processing unit. Each of the one or more processor(s) 602may have numerous arithmetic logic units (ALUs) that perform arithmeticand logical operations, as well as one or more control units (CUs) thatextract instructions and stored content from processor cache memory, andthen executes these instructions by calling on the ALUs, as necessary,during program execution. The processor(s) 602 may also be responsiblefor executing all computer applications stored in the memory 604, whichcan be associated with common types of volatile (RAM) and/or nonvolatile(ROM) memory.

In various examples, memory 604 can include system memory, which may bevolatile (such as RAM), non-volatile (such as ROM, flash memory, etc.)or some combination of the two. The memory 604 can also includeadditional data storage devices (removable and/or non-removable) suchas, for example, magnetic disks, optical disks, or tape. Memory 604 canfurther include non-transitory computer-readable media, such as volatileand nonvolatile, removable and non-removable media implemented in anymethod or technology for storage of information, such as computerreadable instructions, data structures, program modules, or other data.System memory, removable storage, and non-removable storage are allexamples of non-transitory computer-readable media. Examples ofnon-transitory computer-readable media include, but are not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM,digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other non-transitory medium which can be used tostore the desired information and which can be accessed by the basestation 104. Any such non-transitory computer-readable media may be partof the base station 104.

The transmission hardware 606 can include one or more modems, receivers,transmitters, antennas, error correction units, symbol coders anddecoders, processors, chips, application specific integrated circuits(ASICs), programmable circuit (e.g., field programmable gate arrays),firmware components, and/or other components that can establishconnections with one or more UEs 102 and a core network 106, transmitdata, and monitor the connections. The transmission hardware 606 cansupport transmissions in one or more frequency bands using one or morewireless access technologies, as discussed above. At the physical layer310, the transmission hardware 606 can also support transmittingmultiple data streams in parallel in different subcarriers 402 of anOFDM waveform as discussed above, including at different subcarrierspacing values 404 in the same or different frequency bands.

In some examples, service attributes 608 can include information aboutknown services, such service names or associated IP addresses. Serviceattributes 608 can also include parameters associated with such knownservices, such as performance goals or requirements related to latency,reliability, availability, data rate, and/or packet loss, a QCI, QoSparameters, QoE parameters, a priority level, a package length, an SPID,an ARP, and/or other parameters. In other examples, the serviceattributes 608 can include information that can associate QCI flow IDs,service categories, or other attributes of a service with one or moreperformance goals, performance requirements, or specific parameters.

Network attributes 610 can include information about supported frequencybands in licensed and/or unlicensed spectrum, radio frequency linkconditions, key performance indicators, current loads on a base station104 and/or other base stations 104, interference levels, mobilitycapabilities of UEs 102, movement speeds of UEs 102, and/or othernetwork conditions.

Operator policies 612 can include information identifying allowable OFDMnumerologies that are associated with supported frequency bands and/orchannel bandwidths, as well as other policies such as flow controlpolicies, traffic splitting policies, policies related to cell typesand/or wireless access technologies, caching control policies, mobilemanagement policies, service continuity policies, satellite accesspolicies, and fixed broadband access policies.

An OFDM numerology selector 614 can include data and/orcomputer-executable instructions that can determine one or more OFDMnumerologies for communications with a UE 102, based at least in part onservices being used by the UE 102. The OFDM numerology selector 614 canhave components positioned at one or more protocol layers that arehigher than the physical layer 310. For example, in some cases a firstportion of the OFDM numerology selector 614 can be at a 5G NR basestation's upper SDAP layer 302 to analyze data packets and identifytraffic of particular services, a second portion of the OFDM numerologyselector 614 can be at the MAC layer 308 to select one or more specificOFDM numerologies for identified services or service types and toinstruct the physical layer 310 to use to those OFDM numerologies totransmit associated data, and a third portion of the OFDM numerologyselector 614 can be at the RRC layer 312 to send an RRC reconfigurationmessage or other type of message that informs the UE 102 which OFDMnumerologies have been selected. In some cases, portions of the OFDMnumerology selector 614 can also be considered part of a Radio ResourceManager or other element that schedules data transmissions on differentsubcarriers 402.

The OFDM numerology selector 614 can use the service attributes 608 toanalyze data that is to be sent to a UE 102, and identify one or moreassociated performance goals or requirements. The OFDM numerologyselector 614 can select an OFDM numerology for each of the servicesbased on the associated performance goals or requirements. The OFDMnumerology selector 614 can also consider the network attributes 610and/or operator policies 612 when selecting OFDM numerologies for dataof particular services, such as selecting an OFDM numerology for data ofa service that is allowed by an operator policy 612 for a frequency bandthat network attributes 610 indicate is supported and is not currentlycongested.

Example Operations

FIG. 7 depicts a flow chart of an exemplary process for selecting anOFDM numerology for data of a service when a handover operation isperformed. In some examples, the process of FIG. 7 can be performed by abase station 104 when a load control policy reassigns a UE 102 to adifferent network layer and/or wireless access technology, or when a UE102 moves to a new location serviced by a different network layer and/orwireless access technology.

At block 702, the base station 104 can initiate a handover operation fora UE 102. In some examples, the base station 104 may initiate a handoveroperation to transfer communications for the UE 102 to a differentnetwork layer that is supported by that base station 104, such as whensignal quality measurements reported by the UE 102 indicate the UE 102may receive data at a stronger signal strength if the data is sent usinga different frequency band and/or wireless access technology. In otherexamples, the base station 104 may initiate a handover operation when ittakes over communications for the UE 102 from another base station 104based on movement of the UE 102 or a load control policy.

At block 704, the base station 104 can select an OFDM numerology forcommunications with the UE 102. Selection of the OFDM numerology can bebased, at sub-block 706, on service attributes associated with a servicethat the UE 102 is engaged in at the time of the handover operation. Forexample, the UE 102 may be engaged in a service such as a voice call atthe time the base station 104 takes over communications for the UE 102from another base station 104 or transfers the UE's communications to adifferent network layer. The base station 104 can analyze data packetsat a SDAP layer 302 or other protocol layer higher than the physicallayer 310 to identify a service, a service category, a QoS Flow ID,and/or associated performance goals or requirements related to latency,reliability, availability, data rate, and/or packet loss, a QCI, QoSparameters, QoE parameters, a priority level, a package length, an SPID,an ARP, and/or other parameters. In some cases, the core network 106 canreview traffic associated with the UE 102 to determine one or moreservice attributes, and inform the base station 104 of those determinedservice attributes.

The base station 104 can then determine an OFDM numerology associatedwith benefits that can help meet the desired performance goals orrequirements. For example, the base station 104 can determine that datapackets for the UE 102 are associated with a service that has a lowlatency goal, and accordingly select an OFDM numerology associated withshorter OFDM symbols that can be sent more frequently in order to meetthe low latency goal.

In some examples, selection of the OFDM numerology during block 704 canadditionally include selecting the OFDM numerology based on networkattributes at sub-block 708 and/or based on operator policies atsub-block 710. For example, if the handover operation moved the UE 102to an LTE band for which only 15 kHz subcarrier spacing 404 is allowed,the base station 104 can select an OFDM numerology with 15 kHzsubcarrier spacing 404. However, if the handover operation moved the UE102 to a particular 5G NR frequency band that supports more than oneOFDM numerology according to an operator policy, the base station 104can select one of the supported OFDM numerologies for that 5G NRfrequency band.

At block 712, the base station 104 can transmit data for the service tothe UE 102 in subcarriers 402 using the selected OFDM numerology. Thebase station 104 can also send a message to the UE 102 indicating whichOFDM numerology has been selected for the service, such that the UE 102can use that selected OFDM numerology to receive data for the service.For example, the base station 104 can instruct the UE 102 to use theselected OFDM numerology in an RRC reconfiguration message, in DCI inPDCCH, or in any other type of message.

As one non-limiting example, if an OFDM numerology with 15 kHzsubcarrier spacing 404 had been used before the handover operation fordata of a particular service, but the UE 102 has moved into a differentcell that uses a different frequency band that supports 60 kHz and thebase station 104 determines that 60 kHz is best suited to the parametersof the service, the base station 104 can inform the UE 102 that 60 kHzsubcarrier spacing will be used for data of that service following thehandover operation.

As another non-limiting example, if the UE 102 moves from a cell inwhich 15 kHz subcarrier spacing 404 had been used for data of aparticular service to another cell that supports both 15 kHz and 60 kHzsubcarrier spacing 404, but the base station 104 determines that 15 kHzsubcarrier spacing 404 is best suited to the parameters of the service,the base station 104 can continue using 15 kHz subcarrier spacing 404for data of the service following the handover operation. In someexamples, the base station 104 can inform the UE 102 that the samesubcarrier spacing 404 will be used following the handover operation,while in other example the base station 104 may avoid sending such amessage to the UE 102 if the previous subcarrier spacing 404 willcontinue to be used.

In some examples in which handover operations are performed, a basestation 104 can take into a speed of how quickly the UE 102 is moving.For example, if the UE 102 is moving slowly within the same cell servedby the same network layer, the base station 104 may keep the subcarrierspacing 404 constant, or change it less frequently, as the UE 102 movesaround the cell. In contrast, if the UE 102 is on a high speed train andis begin switched between multiple base stations 104 relatively quicklyas it moves, the base stations 104 can change the subcarrier spacing 404relatively often depending on allowable OFDM numerologies associatedwith the specific network layers and policies supported by those basestations 104.

FIG. 8 depicts a flow chart of an exemplary process for assigning OFDMnumerologies for multiple services being used by a single UE 102.

At block 802, a base station 104 can determine that a UE 102 is engagedin multiple services by analyzing data for the UE 102 at an SDAP layer302 and/or other protocol layers above the physical layer 310. Forexample, the base station 104 can review data packets addressed to theUE 102 at an SDAP layer 302, determine that the data packets areassociated with two QoS Flow IDs, and accordingly determine that the UEis engaged in two different services. In some examples, the core network106 can determine that the UE 102 is engaged in multiple services, andinform the base station 104 along with any attributes of those servicesdetermined by the core network 106. In some examples, the base station104 or core network 106 can group one or more of the multiple servicesinto the same group, such as groups corresponding to eMBB, URLLC, mMTC,or M-IoT categories.

At block 804, the base station 104 can select an OFDM numerology fordata associated with individual ones of the multiple services, or agroup of services. Selection of an OFDM numerology for a particularservice or group of services can be based, at sub-block 806, on serviceattributes associated with the particular service or group of services.For example, the base station 104 can analyze data packets at a SDAPlayer 302 or other protocol layer higher than the physical layer 310 toidentify a service, a service category, a QoS Flow ID, and/or associatedperformance goals or requirements related to latency, reliability,availability, data rate, and/or packet loss, a QCI, QoS parameters, QoEparameters, a priority level, a package length, an SPID, an ARP, and/orother parameters. In some cases, the core network 106 can review trafficassociated with the UE 102 to determine one or more service attributes,and inform the base station 104 of those determined service attributes.In some examples, the core network 106 can also indicate when serviceattributes of multiple services indicate that those multiple servicesshould be grouped together or should be considered separately during thefollowing blocks.

The base station 104 can then determine an OFDM numerology associatedwith benefits that that can help meet the desired performance goals orrequirements. For example, the base station 104 may determine that somedata packets for the UE 102 are associated with a first service that hasa low latency goal, while other data packets for the UE 102 areassociated with a second service that uses a large package length.Accordingly, the base station 104 can select a first OFDM numerologyassociated with shorter OFDM symbols for the first service, in order tomeet the first service's low latency goal, while selecting a second OFDMnumerology associated with longer OFDM symbols for the second servicethat correspond to the second service's larger package length. In otherexamples, the base station 104 can determine that multiple services in agroup share at least some service attributes, or can have been informedby the core network 106 that the multiple services should be grouped,and can select a shared OFDM numerology for all of the services in thatgroup.

In some examples, selection of OFDM numerologies for individual servicesor groups of services during block 804 can additionally includeselecting the OFDM numerologies based on network attributes at sub-block808 and/or based on operator policies at sub-block 810. For example, ifnetwork attributes indicate that a particular 5G NR frequency band issupported by the base station and an operator policy allows 30 kHz, 60kHz, or 120 kHz subcarrier spacing 404 on that frequency band, the basestation 104 can select one of 30 kHz, 60 kHz, or 120 kHz subcarrierspacing 404 for a particular service or group of services, whileselecting between allowable subcarrier spacing 404 values on the same ordifferent bands for other services or groups of services.

At block 812, the base station 104 can transmit data for the services tothe UE 102 in subcarriers 402 using the selected OFDM numerologies. Insome cases, the base station 104 can send a message to the UE 102indicating which OFDM numerologies have been selected for the servicesor groups of services, such that the UE 102 can use that selected OFDMnumerologies to receive data for the services or groups of services.

As noted above, if the base station 104 determines that the same OFDMnumerology should be used for a group of services that the UE is usingsimultaneously, the base station 104 can use the same OFDM numerologyfor transmissions associated with all of those services, in the samefrequency band or in different frequency bands. For example, the basestation 104 can determine that a UE 102 is engaged in multiple eMBBservices, and accordingly use the same OFDM numerology to transmit dataof those eMBB services. However, in other examples a base station 104can determine that a UE 102 is engaged in multiple eMBB services, butdetermine that some have lower latency requirements than others.Accordingly, the base station 104 can use OFDM numerologies that providelower latency benefits for those services, while using different OFDMnumerologies for other services that do not rely on low latencytransmissions.

CONCLUSION

As described above, a base station 104 can select an OFDM numerology fortransmissions to a UE 102 based at least in part on attributes of one ormore services being used by the UE 102. In some cases, the base station104 can additionally consider network attributes and/or operatorpolicies when selecting OFDM numerologies.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter is not necessarily limited to the specificfeatures or acts described above. Rather, the specific features and actsdescribed above are disclosed as example embodiments.

What is claimed is:
 1. A method, comprising: receiving, by a basestation of a telecommunication network, at least one data packet passingthrough the base station, wherein the at least one data packet isassociated with a service for a user equipment (UE) connected to thebase station; determining, by the base station and based on the at leastone data packet, one or more service attributes of the service;identifying, by the base station and based on the one or more serviceattributes, one or more performance goals associated with the service;selecting, by the base station, a numerology that corresponds to the oneor more performance goals, wherein the numerology indicates a subcarrierspacing; and transmitting, by the base station at a physical layer of aprotocol stack, data associated with the service to the UE in at leastone subcarrier spaced apart from adjacent subcarriers by the subcarrierspacing.
 2. The method of claim 1, wherein the numerology is anorthogonal frequency-division multiplexing (OFDM) numerology.
 3. Themethod of claim 1, wherein the determining comprises analyzing the atleast one data packet at a second layer of the protocol stack, differentfrom the physical layer, to determine the one or more service attributesof the service.
 4. The method of claim 1, wherein the selectingcomprises determining, at a Media Access Control (MAC) layer of theprotocol stack, the numerology that corresponds to the one or moreperformance goals.
 5. The method of claim 1, further comprisingtransmitting, by the base station to the UE, an indication of thenumerology selected by the base station.
 6. The method of claim 1,wherein the numerology is different than a default numerology assignedupon an initial attachment of the UE to the base station.
 7. The methodof claim 1, wherein the selecting and the transmitting is performedfollowing initiation of a handover operation associated with changing atleast one of a frequency band or a wireless access technology used bythe UE to connect to the telecommunication network.
 8. The method ofclaim 1, wherein the one or more service attributes includes one or moreof a Quality of Service (QoS) Flow Identifier, a QoS Class Identifier(QCI), QoS parameters, Quality of Experience (QoE) parameters, apriority level, a package length, a Service Profile Identifier (SPID),or an Allocation and Retention Policy (ARP).
 9. The method of claim 1,wherein the one or more performance goals associated with the serviceare associated with one or more of latency, reliability, availability,data rate, or packet loss.
 10. The method of claim 1, furthercomprising: determining, by the base station, a service categoryassociated with the service, based on the one or more serviceattributes; determining, by the base station, a set of allowablenumerologies that correspond to the service category; and selecting, bythe base station, the numerology from among the set of allowablenumerologies based on the one or more performance goals.
 11. The methodof claim 1, further comprising: receiving, by the base station, at leastone second data packet passing through the base station, wherein the atleast one second data packet is associated with a second service for theUE connected to the base station; determining, by the base station andbased on the at least one second data packet, one or more second serviceattributes of the second service; identifying, by the base station andbased on the one or more second service attributes, one or more secondperformance goals associated with the second service; determining, bythe base station, that the one or more second performance goalscorrespond to the one or more performance goals of the service;determining, by the base station, to use the numerology in associationwith both the service and the second service; and transmitting, by thebase station at the physical layer, the data associated with the serviceand second data associated with the second service to the UE in the atleast one subcarrier based on the subcarrier spacing indicated in thenumerology.
 12. The method of claim 1, further comprising: receiving, bythe base station, at least one second data packet passing through thebase station, wherein the at least one second data packet is associatedwith a second service for the UE connected to the base station;determining, by the base station and based on the at least one seconddata packet, one or more second service attributes of the secondservice; identifying, by the base station and based on the one or moresecond service attributes, one or more second performance goalsassociated with the second service; determining, by the base station,that the one or more second performance goals are different from the oneor more performance goals of the service; selecting, by the basestation, a second numerology that corresponds to the one or more secondperformance goals, wherein the second numerology indicates a secondsubcarrier spacing different from the subcarrier spacing; andtransmitting, by the base station at the physical layer, second dataassociated with the second service to the UE in at least one secondsubcarrier spaced apart from other adjacent subcarriers by the secondsubcarrier spacing.
 13. A base station of a telecommunication network,comprising: one or more processors; transmission components configuredto wirelessly connect the base station to a user equipment (UE) at aphysical layer of a protocol stack using a wireless access technology;memory storing computer-executable instructions that, when executed bythe one or more processors, cause the base station to perform operationscomprising: receiving at least one data packet passing through the basestation, wherein the at least one data packet is associated with aservice for the UE; determining, based on the at least one data packet,one or more service attributes of the service; identifying, based on theone or more service attributes, one or more performance goals associatedwith the service; selecting a numerology that corresponds to the one ormore performance goals, wherein the numerology indicates a subcarrierspacing; and transmitting, at the physical layer, data associated withthe service to the UE in at least one subcarrier spaced apart fromadjacent subcarriers by the subcarrier spacing.
 14. The base station ofclaim 13, wherein the determining comprises analyzing the at least onedata packet at a second layer of the protocol stack, different from thephysical layer, to determine the one or more service attributes of theservice.
 15. The base station of claim 13, wherein the numerology isdifferent than a default numerology assigned upon an initial attachmentof the UE to the base station.
 16. The base station of claim 13, whereinthe operations further comprise: determining a service categoryassociated with the service, based on the one or more serviceattributes; determining a set of allowable numerologies that correspondto the service category; and selecting the numerology from among the setof allowable numerologies based on the one or more performance goals.17. One or more non-transitory computer-readable media storingcomputer-executable instructions that, when executed by one or moreprocessors of a base station of a telecommunication network, cause thebase station to perform operations comprising: receiving at least onedata packet passing through the base station, wherein the at least onedata packet is associated with a service for a user equipment (UE)connected to the base station; determining, based on the at least onedata packet, one or more service attributes of the service; identifying,based on the one or more service attributes, one or more performancegoals associated with the service; selecting a numerology thatcorresponds to the one or more performance goals, wherein the numerologyindicates a subcarrier spacing; and transmitting, at a physical layer ofa protocol stack, data associated with the service to the UE in at leastone subcarrier spaced apart from adjacent subcarriers by the subcarrierspacing.
 18. The one or more non-transitory computer-readable media ofclaim 17, wherein the determining comprises analyzing the at least onedata packet at a second layer of the protocol stack, different from thephysical layer, to determine the one or more service attributes of theservice.
 19. The one or more non-transitory computer-readable media ofclaim 17, wherein the numerology is different than a default numerologyassigned upon an initial attachment of the UE to the base station. 20.The one or more non-transitory computer-readable media of claim 17,wherein the operations further comprise: determining a service categoryassociated with the service, based on the one or more serviceattributes; determining a set of allowable numerologies that correspondto the service category; and selecting the numerology from among the setof allowable numerologies based on the one or more performance goals.